Connecting message media with shared digital media

ABSTRACT

A digital media sharing system (“DMSS”) for creating, transmitting and receiving digital media data (“DMD”) with message media (MM) files attached thereto. Said message Media may reside locally or on a server prior to being connected to said digital media data.

1. PRIORITY

This application claims the benefit of U.S. provisional patentapplication 61/401,229 filed Aug. 9, 2010 entitled “ADDING MESSAGECONTENT TO SHARED DIGITAL MEDIA” the entirety of which (specification,claims, figures, appendices and abstract) is hereby incorporated by thisreference as if fully set forth herein.

FIELD

This disclosure relates generally to targeted advertising and inparticular to a method and system for adding message media to digitalmedia that is shared.

BACKGROUND

At present, the growth of telecommunication networks has allowed agrowing number of people to communicate with each other in manydifferent ways. These telecommunication networks have allowed people tocommunicate in ways that vary from voice telephony to data and mediasharing. Global communication networks such as the Internet haveproduced communication options such as email, file transfer protocol(“ftp”), personal websites, online forums, chat services, peer-to-peerservices, instant messenger services (such as messenger servicesprovided by Yahoo®, Microsoft®, Google®, etc), streaming media services(such as Youtube®), voice-over IP (“VoIP”)(such as Skype®, Vonage®,etc), Internet video conferencing, social networking services (such asTwitter®, Linkedin®, Facebook®, etc.), etc.

Other telecommunication networks such as some of the cellulartelecommunication networks have also increased the ways that their userscan communicate with each other (such as text messaging, media sharingservices, etc.) and with external communication networks such as theInternet. As a result, at present, the sharing of digital media hasbecome a growing cultural trend both on the Internet and cellulartelephone networks.

Advertising and/or branding is constantly seeking new ways to placemessages in front of the population of targeted potential consumerswhich are within selected demographics. Youtube® for example streamsgoogle links with playback online of some files.

As such, there is a need for a system and method for connecting messagemedia with shared digital media content through a communicationinfrastructure that is secure and does not have any of the drawbacks ofthe prior art services.

DESCRIPTION

A digital media sharing system (“DMSS”) for receiving digital media data(“DMD”) produced by a media device is described. The DMSS may include anetwork, a first set-top box in signal communication with the network, afirst rendering device in signal communication with the set-top box andthe network, and a storage device in signal communication with theset-top box and the network. The first set-top box may be configured toreceive the DMD from the media device and the rendering device may beconfigured to render the received DMD. The storage device may beconfigured to store the rendered DMD.

In some exemplary implementations, and one or more aspects associatedtherewith, set forth is a DMSS for receiving digital media data producedby a media device, the DMSS including a network; a first set-top box insignal communication with the network, wherein the first set-top box isconfigured to receive the digital media data from the media device; afirst rendering device in signal communication with the set-top box andthe network, wherein the rendering device is configured to render thereceived digital media data; a storage device in signal communicationwith the set-top box and the network, wherein the storage device isconfigured to store the rendered digital media data; and the network isa cable communication network that is in signal communication with aplurality of set-top boxes.

In some exemplary implementations, and one or more aspects associatedtherewith, an ad-on message file such as a video trailer, advertisement,logo, brand or bug is affixed and incorporated into the uploaded DMDfile. The addition of a specific message file may correlate to paidadvertisement/placement.

In some exemplary implementations, and one or more aspects associatedtherewith, an ad-on message file such as a video trailer, advertisement,logo, brand or bug is affixed and incorporated into the DMD file duringrendering and/or preparation for sharing. The addition of a specificmessage file may correlate to paid advertisement/placement.

In some exemplary implementations, and one or more aspects associatedtherewith, an ad-on message file such as a audio file, video trailer,advertisement, logo, brand or bug is affixed and incorporated into theDMD file on the share side of the share. The addition of a specificmessage file may correlate to paid advertisement/placement.

In some exemplary implementations, and one or more aspects associatedtherewith, an ad-on message file such as a video trailer, advertisement,logo, brand or bug is affixed and incorporated into the DMD file on thesharer side of the share. The addition of a specific message file maycorrelate to paid advertisement/placement.

In some exemplary implementations, and one or more aspects associatedtherewith, is set forth a DMSS for receiving digital media data producedby a media device, the DMSS including a network; a first set-top box insignal communication with the network, wherein the first set-top box isconfigured to receive the digital media data from the media device; afirst rendering device in signal communication with the set-top box andthe network, wherein the rendering device is configured to render thereceived digital media data; a storage device in signal communicationwith the set-top box and the network, wherein the storage device isconfigured to store the rendered digital media data; the network is acable communication network that is in signal communication with aplurality of set-top boxes; and there is at least one server in signalcommunication with the cable communication network and wherein the firstrendering device is external to the first set-top box and is in signalcommunication with the server. In some implementations the storagedevice is external to the first set-top box and is in signalcommunication with the server. In some implementations there is a secondset-top box of the plurality of set-top boxes, wherein the secondset-top box is configured to receive the rendered digital media datafrom the storage device. In some implementations a second renderingdevice located within a second set-top box of the plurality of set-topboxes. In some aspects the storage device is external to the firstset-top box and is in signal communication with the server. In someimplementations the second set-top box is configured to receive therendered digital media data from the storage device. In someimplementations a third set-top box of the plurality of set-top boxes,wherein the third set-top box is in signal communication with thenetwork, and wherein the third set-top box is configured to receive therendered digital media data from the storage device.

In some exemplary implementations, and one or more aspects associatedtherewith, set forth is a method for sharing digital media data producedby a media device over a network having a plurality of set-top boxes,the method including; receiving the digital media data at a firstset-top box of the plurality of set-top boxes; rendering the receiveddigital media data; storing the rendered digital media data on a storagedevice; and, the network is a cable communication network that is insignal communication with the plurality of set-top boxes. In someimplementations storing includes storing the rendered digital media dataon a storage device located within the first set-top box and renderingincludes rendering the received digital media data in a file format thatis usable by the storage device. In some implementations an accessiblemenu that is displayed on a display in signal communication with thefirst set-top box is produced, wherein the accessible menu displays aconfirmation of the storage of the rendered digital media data. In someimplementations the server is queried for at least one file formatusable by the targeted storage device.

In some implementations receiving the rendered digital media data fromthe storage device is at least one second set-top box from the pluralityof set-top boxes. In some implementations rendering the received digitalmedia data is within at least one of the first set-top box and a secondset-top box of the plurality of set-top boxes.

Other devices, apparatus, systems, methods, features and advantages ofthe disclosure will be or will become apparent to one with skill in theart upon examination of the following figures and detailed description.It is intended that all such additional systems, methods, features andadvantages be included within this description, be within the scope ofthe disclosure, and be protected by the accompanying claims.

FIGURES

The disclosure may be better understood by referring to the followingfigures. The components in the figures are not necessarily to scale,emphasis instead being placed upon illustrating the principles of thedisclosure. In the figures, like reference numerals designatecorresponding parts throughout the different views. All callouts in anyappendices and/or figures are hereby incorporated by this reference.

FIG. 1 is a system block diagram of an example of an implementation ofdigital media sharing system (“DMSS”) for receiving digital media dataproduced by a media device, in accordance with the disclosure.

FIG. 2 is a block diagram of an example of an implementation ofutilizing the DMSS of FIG. 1 for capturing and rendering recorded videoproduced a the media device.

FIG. 3 shows a flow chart illustrating an example process performed bythe DMSS described in FIGS. 1 and 2 in accordance with the disclosure.

FIG. 4 shows a block diagram of an example of an implementation of DMSSto share DMD between STBs, mobile devices, and archives in accordancewith the disclosure.

FIGS. 5 through 16 show examples of screen shots of a Graphic userinterface to some aspects of the disclosure.

FIG. 17 represents a DMD file without additive trailer/ad.

FIG. 18 represents a DMD file with additive trailer/ad.

FIG. 19 represents a DMD file with a time gap designated to fill with alocal additive trailer/ad.

FIG. 20-22 represents a DMD file with overlay or additive bug, logo adand the like.

All descriptions and callouts in the Figures are hereby incorporated bythis reference as if fully set forth herein.

FURTHER DESCRIPTION

In the following description of examples of implementations, referenceis made to the accompanying drawings that form a part hereof, and whichshow, by way of illustration, specific implementations of the presentdisclosure that may be utilized. Other implementations may be utilizedand structural changes may be made without departing from the scope ofthe present disclosure.

In general, a digital media sharing system (“DMSS”) for receivingdigital media data produced by a media device is disclosed. The DMSS mayshare the digital media data (“DMD”) with a number of users and/or storethe DMD in varying types of storage devices. In general, the DMSS mayinclude a network, a first set-top box (“STB”), a first renderingdevice, and a storage device. The first STB may be in signalcommunication with the network. The first rendering device may be insignal communication with the STB and the network. The storage devicemay also be in signal communication with the STB and the network. Thefirst STB is configured to receive the DMD from the media device and therendering device is configured to render the received DMD. The storagedevice is configured to store the rendered DMD. Moreover, in addition tothe first STB, the DMSS may also include other STBs in signalcommunication with the network. As an example of operation, the DMSS mayperform a method that includes receiving the DMD at the first STB of theplurality of STBs, rendering the received DMD, and then storing therendered DMD on a storage device.

Turning to FIG. 1, a system block diagram is shown of an example of animplementation of DMSS 100 in accordance with the disclosure. The DMSS100 may include a first STB 102 in signal communication with a network104, display 106, and media device 108 via signal paths 110, 112, and114, respectively. The DMSS 100 may also include a server 116, a secondSTB 118, second display 120, a third STB 122, third display 124, anN^(th) STB 126, and an N^(th) display 128. The network 104 may be insignal communication with the server 116, second STB 118, third STB 122,and the N^(th) STB 126 via signal paths 130, 132, 134, and 136,respectively. The first STB 102 may also be in signal communication witha first STB storage 138 and the server may be in signal communicationwith a server storage 140 via signal paths 142 and 144, respectively.Similarly each STB from the second STB 118 to the N^(th) STB 122 mayalso have an associated STB storage (not shown) in signal path with eachcorresponding STB.

It is appreciated by those skilled in the art that the circuits,components, modules, and/or devices of the DMSS 100 are described asbeing in signal communication with each other, where signalcommunication refers to any type of communication and/or connectionbetween the circuits, components, modules, and/or devices that allows acircuit, component, module, and/or device to pass and/or receive signalsand/or information from another circuit, component, module, and/ordevice. The communication and/or connection may be along any signal pathbetween the circuits, components, modules, and/or devices that allowssignals and/or information to pass from one circuit, component, module,and/or device to another and includes wireless or wired signal paths.The signal paths may be physical such as, for example, conductive wires,electromagnetic waveguides, attached and/or electromagnetic ormechanically coupled, terminals, semi-conductive or dielectric materialsor devices, or other similar physical connections or couplings.Additionally, signal paths may be non-physical such as free-space (inthe case of electromagnetic propagation) or information paths throughdigital components where communication information is passed from onecircuit, component, module, and/or device to another in varying digitalformats without passing through a direct electromagnetic connection.

As an example, the first STB 102, second STB 118, third STB 120, andN^(th) STB 122 may all be typical STBs utilized either by a cabletelevision provider (“CTP”) such as, for example, Cox Communication,Time Warner Cable, Comcast, etc., a satellite television provider(“STP”) such as, for example, DISH Network®, DIRECTV®, etc., or othertype of network television provider (such as television visa DSL) thatrequires that end user use an STB to receive television content (analog,digital, or both) from a propriety communication network that can bedisplayed on a display in signal communication with the STB. In theexample of a CTP, the STB is generally known as a “cable box.” The STBmay be any device capable of receiving television programming with oneor more video tuners and processor(s) and a device address. STB's alsoinclude gaming systems, gaming units like PlayStation®, Nintendo®,Xbox®, Wii®, DVR, Apple® tv, or the like. Typically, STBs includestorage capacity (such as first STB storage 138) for storing shared DMDand/or for buffering shared DMD. Generally, STBs are devices that haveassigned MAC addresses, IP addresses, access IDs, and serial numbersthat are specific to the STB and are a form of identity information tothe CTP or STP

The media device 108 is a detachable device that may be any type ofvideo device including, for example, a video camera (such as an analogor digital camcorder), digital camera with video capability, a videoenable cellular telephone, etc.

Each transforming of DMD from one device or form to another device orform is an opportunity for the CTP or STP to form a new revenue streameither through a per event charge or recurring charge for access to theportions of the hardware and software within the CTP or STPinfrastructure. Media device(s) 108 well suited to mate, merge orconnect or otherwise interface with said CTP or STP for optimalrendering and/or transfer provide additional opportunity for said CTP orSTP to derive revenue streams from per use, recurring, sales, leasing orrental.

The network 104 may be any propriety communication network such as forexample, a CTP network and/or STP network. The network 104 may includeaccess to travel through non-propriety communication networks such asthe Internet or cellular telephone networks.

The first display 106, second display 124, third display 126, and N^(th)display 128 may be any generally know video display that is capable ofdisplay visual programming and information produced by the correspondingSTB 102, 118, 120, and 122, respectively. Examples of these types ofvideo displays include analog and/or digital televisions, displaymonitors, computer monitors, etc.

The server 116 may be any server or combination of servers utilized bythe CTP or STP for accessing and/or controlling the network 104. In thecase of a CTP and/or STP, the server 116 may include the communicationand processing equipment utilized by the CTP and/or STP to generate,control, and/or save DMD on the DMSS 100. Said server or any portionthereof may be targeted for use for a particular storage task.

The first STB storage 138, server storage 140, and other storage devices(not shown) corresponding to the other STBs 118, 120, and 122, may bememory devices capable of storing DMD. The STB storage 138 (and thestorage of the other STBs 118, 120, and 122) may be memory devices thatmay be either internal to the first STB 102 and other corresponding STBs118, 120, and 122, or external based on the preference of the user ofthe corresponding STB and the capabilities offered by the respective CTPand/or STP. Examples of the these types of storage may include, forexample, computer hard-drives and/or RAM memory. In the case of thefirst STB storage 138, it may be a hard-drive located internal to thefirst STB 102 or it could optionally be an external storage unit such asan external hard-drive. In the case of the server 116, the serverstorage 140 may also be an internal hard-drive to the server 116,external hard-drive, or it could be one or more storage servers (notshown) that include multiple hard-drives each.

The first STB 102, second STB 118, third STB 120, N^(th) STB 122, andserver 116 may each have processor (not shown) capable of processing(such, as for example, capturing, converting, and/or rendering) ofreceiving video data from the media device 108 and converting it to DMDand/or converting the DMD into another format for video processing oroptimized for storage on the first STB storage 138, server storage 140,other storage devices, or combination of storage devices. The processormay act as a rendering device that is configured to render any receivedvideo from the media device 108 to produce the DMD. The processor mayalso act a parallel processing rendering device wherein a processor fora given device (such as the first STB 102) may act in parallel with theprocessor (not shown) of the server 116 and/or other processors (notshown) of the other STBs 118, 120, and 122 to render the video or DMDquicker than would be possible by just one single processor. Theprocessor may be any general purpose processor such as for example ancentral processor unit (“CPU”), an application specific integrated chip(“ASIC”), digital signal processor (“DSP”), reduced instruction set(“RISC”) processor, microprocessor, or other similar devices.

As an example of operation, the DMSS 100 may perform a method thatincludes receiving the DMD at the first STB 102 of the plurality ofSTBs, rendering the received DMD, and then storing the rendered DMD on astorage device. The storage device may be the first STB storage 138,server storage 140, a storage device corresponding to the other STBs, ora combination of these.

More specifically, if a user captures video with the media device 108(such as, for example, recording video with a video camera) and thenconnects the media device 108 to the first STB 102 via the signal path114 (which may be via a universal serial bus (“USB”), HDMI, Firewire®,eSATA, IEEE 802.11, Bluetooth®, Ethernet, LAN, white space device, orother type of wired or wireless connection), the user can upload his/herrecorded video to the first STB 102. The recorded video uploaded via aninput video signal 146 that may be analog or digital based on the typeof device utilized as the media device 108. The input video signal 146is received by the first STB 102 which may process the input videosignal 146 to produce a DMD signal which may be sent 148 along signalpath 142 to be stored in the first STB storage 138 and/or sent 150 alongsignal path 112 to be displayed on the first display 106. Alternatively,the DMD may be sent 152 from the first STB 102 along signal path 110through the network 104 to either the server 116, one of more STBs (suchas 118, 120, and 122), or combination of either server 116 and STBs ormultiple STBs based on the utilization of the other processors in theserver 116 or other STBs 118, 120, and 122.

In general, the first STB 102 includes software with drivers which arecapable of auto-detecting the type of device that the media device 108is when it is connected to the first STB 102. The STB 102 may include adriver database with different drivers corresponding to different mediadevices. Once the proper driver is installed in the first STB 102, thefirst STB 102 is able to copy or capture video 146 received from themedia device 108. The first STB 102 is then configured to encode thevideo 146 in real-time utilizing a tuner or other video specific devicesuch as video encoder, processor or chip designed for video capture. Itis appreciated that the encoding can be shared between the first STB102, the other STBs 118, 120, and 122 and/or the server 116 based onusage of the different processors in the different devices. Once theencoding have been completed, the first STB 108 is configured to storethe DMD on the first STB storage 138 and/or remote storage such asserver storage 140 and/or other storage devices on the other STBs 118,120, and 122. To connect to a remote storage, the first STB 108 mayutilize network security credential such as, for example, peer name,password and MAC address to authentic peer.

In FIG. 2, a block diagram is shown of an example of an implementationof utilizing the DMSS 200 for capturing and rendering recorded video 146produced by the media device 108. In this example, the first STB 102 mayinclude a first renderer 202 that is in signal communication with thefirst STB 102 via signal path 204. The first renderer 202 may be module,circuit, component, and/or device located internal to the first STB 102or may be an external device. The server 116 may also include a serverrenderer 206 in signal communication with the server 116 via signal path208. Similar to the first renderer 202, the server renderer 206 may bemodule, circuit, component, and/or device located internal to the server116 or may be an external device. The second STB 118 may include asecond renderer 206 and a second STB storage 212 in signal communicationwith the second STB 118 via signal paths 214 and 216, respectively.Similar to the first renderer 202, the second renderer 206 may bemodule, circuit, component, and/or device located internal to the secondSTB 118 or may be an external device. Similar to first STB storage 138,the second STB storage 118 may be a memory device capable of storing theDMD. The second STB 118 may be a memory device that may be eitherinternal to the second STB storage 118 or external based on thepreference of the user of the second STB storage 118 and thecapabilities offered by the respective CTP and/or STP. Examples of thesecond STB storage 118 may include, for example, computer hard-drivesand/or RAM memory, which may be a hard-drive located internal to thesecond STB storage 118 or it could optionally be an external storageunit such as an external hard-drive.

Similar to the second STB 118, the third STB 120 may include a thirdrenderer 218 and a third STB storage 220 in signal communication withthe third STB 120 via signal paths 222 and 224, respectively. Similar tothe first renderer 202, the third renderer 218 may be module, circuit,component, and/or device located internal to the third STB 120 or may bean external device. Similar to first STB storage 138, the third STB 120may be a memory device capable of storing the DMD. The third STB 120 maybe a memory device that may be either internal to the third STB 120 orexternal based on the preference of the user of the third STB 120 andthe capabilities offered by the respective CTP and/or STP. Examples ofthe third STB 120 may include, for example, computer hard-drives and/orRAM memory, which may be a hard-drive located internal to the third STB120 or it could optionally be an external storage unit such as anexternal hard-drive.

In an example of operation, a user of the first STB 102 may detachablyconnect a media device 108 (such as a camcorder, digital camera withvideo capability, cellular telephone with video capability, etc.) withrecorder video to the first STB 102. As stated earlier, once connectedthe media device 108 may be in signal communication with the first STB102 via the detachable connected signal path 114, which may be via aUSB, HDMI, Firewire®, eSATA, IEEE 802.11, Bluetooth®, Ethernet, LAN,white space device, or other type of wired or wireless connection. Theuser of the first STB 102 can then upload his/her recorded video to thefirst STB 102 from the media device 108 via the input video signal 146,which may be an analog or digital video signal based on the type ofdevice utilized as the media device 108. The input video signal 146 isreceived by the first STB 102 which may process the input video signal146 to produce a DMD signal which may be sent 148 along signal path 142to the first STB storage 138 for storage at the first STB 102 and/orsent 152 and 226 from the first STB 102 along signal path 110 throughthe network 104 and signal path 130 to the server 116. Alternatively,the DMD signal may be sent 152 and 228 from the first STB 102 alongsignal path 110 through the network 104 and signal path 132 to thesecond STB 118; or the DMD signal may be sent 152 and 230 from the firstSTB 102 along signal path 110 through the network 104 and signal path134 to the third STB 120. The chosen path for the DMD signal maydetermined by a controller (not shown) in either the first STB 102 orserver 116 based on system resources of the DMSS 100. The controller maybe a microprocessor, microcontroller, processor, DSP, ASIC, RISCprocessor, or other type of similar processor. The controller may bepart of or in signal communication with a processor (not shown) locatedat either first STB 102 or server 116.

Storage of Digital Media Data within the Network

Based on the system resources of the DMSS 100, if the controllerdetermines that the DMD signal is to be processed exclusively within thefirst STB 102, the first STB 102 receives the input video signal 146from the media device 108 and processes it via the first renderer 202.The first renderer 202 may first capture and convert the input videosignal 146 from an analog video signal to a digital video signal basedon whether the media device 108 is an analog video device. If the mediadevice 108 is a digital device, then the first renderer 202 does nothave to capture and convert the input video signal 146 except forpossibly converting the input video signal 146 from the digital formatutilized by the media device 108 to another digital format more suitablefor processing and storing by the first STB 102. The digital videosignal may then be rendered by the first renderer 202 to produce the DMDsignal 148 which may be passed to the first STB storage 138 via signalpath 142. In this manner the first STB storage 138 may act as a localarchive for DMD that is uploaded by the user utilizing the media device108.

If the controller determines, based on the system resources of the DMSS100, that the DMD signal is to processed by the first STB 102 but storedon the server storage 140, the first STB 102 receives the input videosignal 146 from the media device 108 and processes it via the firstrenderer 202. The first renderer 202 may first capture and convert theinput video signal 146 from an analog video signal to a digital videosignal based on whether the media device 108 is an analog video device.Again, if the media device 108 is a digital device, then the firstrenderer 202 does not have to capture and convert the input video signal146 except for possibly converting the input video signal 146 from thedigital format utilized by the media device 108 to another digitalformat more suitable for processing and storing by the first STB 102and/or server 116. The digital video signal may then be rendered by thefirst renderer 202 to produce the DMD signal 152, 226, and 232 which maybe passed to the server storage 140 via signal paths 110, 130, and 144,network 104, and server 116. In this manner the server storage 140 mayact as a remote archive for the DMD that is uploaded by the userutilizing the media device 108. If a specific remote archive provider ofarchive server is particularly identified for an archive task thatserver may be referred to as targeted.

If the controller determines, based on the system resources of the DMSS100, that the DMD signal is to processed by the first STB 102 but storedon the second STB storage 212, the first STB 102 receives the inputvideo signal 146 from the media device 108 and processes it via thefirst renderer 202. The first renderer 202 may first capture and convertthe input video signal 146 from an analog video signal to a digitalvideo signal based on whether the media device 108 is an analog videodevice. Again, if the media device 108 is a digital device, then thefirst renderer 202 does not have to capture and convert the input videosignal 146 except for possibly converting the input video signal 146from the digital format utilized by the media device 108 to anotherdigital format more suitable for processing and storing by the first STB102 and/or second STB 118. The digital video signal may then be renderedby the first renderer 202 to produce the DMD signal 152, 228, and 234which may be passed to the second STB storage 212 via signal paths 110,132, and 216, network 104, and second STB 118. In this manner the secondSTB storage 212 may act as a remote archive for the DMD that is uploadedby the user utilizing the media device 108.

Similarly, if the controller determines, based on the system resourcesof the DMSS 100, that the DMD signal is to processed by the first STB102 but stored on the third STB storage 220, the first STB 102 receivesthe input video signal 146 from the media device 108 and processes itvia the first renderer 202. The first renderer 202 may first capture andconvert the input video signal 146 from an analog video signal to adigital video signal based on whether the media device 108 is an analogvideo device. Again, if the media device 108 is a digital device, thenthe first renderer 202 does not have to capture and convert the inputvideo signal 146 except for possibly converting the input video signal146 from the digital format utilized by the media device 108 to anotherdigital format more suitable for processing and storing by the first STB102 and/or third STB storage 220. The digital video signal may then berendered by the first renderer 202 to produce the DMD signal 152, 230,and 236 which may be passed to the third STB storage 220 via signalpaths 110, 134, and 224, network 104, and third STB 120. In this mannerthe third STB 120 may act as a remote archive for the DMD that isuploaded by the user utilizing the media device 108.

Rendering Digital Media Data within the Network Rendering at the ServerRenderer

Based on the system resources of the DMSS 100, if the controllerdetermines that the DMD signal is to be processed external to the firstSTB 102 at the server renderer 206, the first STB 102 receives the inputvideo signal 146 from the media device 108 and processes it via thefirst renderer 202. The first renderer 202 may first capture and convertthe input video signal 146 from an analog video signal to a digitalvideo signal based on whether the media device 108 is an analog videodevice. If the media device 108 is a digital device, then the firstrenderer 202 does not have to capture and convert the input video signal146 except for possibly converting the input video signal 146 from thedigital format utilized by the media device 108 to another digitalformat more suitable for processing by the server renderer 206. Thefirst STB 102 then sends the digital video signal to the server renderer206 via signal paths 110, 130, and 208 and through the network 104 andserver 116. The digital video signal may then be rendered by the serverrenderer 206 to produce the DMD signal 232 which may be passed to theserver storage 140 via signal path 144 or back to the first STB 102 andstored via the first STB storage 138. In this manner the server renderer206 acts as a remote processor capable of processing the digital videosignal with processing power that is typically greater than that of theprocessor of the first renderer 202. In this example, the first STBstorage 138 may act as a local archive for DMD that is processed by theserver renderer 206 or the server storage 140 may act as a remotearchive for DMD that is processed by the server renderer 206.

Rendering at the Second STB

If, instead, the controller determines that the DMD signal is to beprocessed external to the first STB 102 at the second STB renderer 212,the first STB 102 receives the input video signal 146 from the mediadevice 108 and processes it via the first renderer 202. The firstrenderer 202 may first capture and convert the input video signal 146from an analog video signal to a digital video signal based on whetherthe media device 108 is an analog video device. If the media device 108is a digital device, then the first renderer 202 does not have tocapture and convert the input video signal 146 except for possiblyconverting the input video signal 146 from the digital format utilizedby the media device 108 to another digital format more suitable forprocessing by the server renderer 206. The first STB 102 then sends thedigital video signal to the second STB renderer 212 via signal paths110, 132, and 216 and through the network 104 and second STB 118. Thedigital video signal may then be rendered by the second STB renderer 212to produce the DMD signal 234 which may be passed to the second STBstorage 212 via signal path 216 or back to the first STB 102 and storedvia the first STB storage 138. Similarly to the previous example, inthis manner the second STB renderer 212 acts as a remote processorcapable of processing the digital video signal. In this example, thefirst STB storage 138 may act as a local archive for DMD that isprocessed by the second STB renderer 212 or the second STB storage 212may act as a remote archive for DMD that is processed by the second STBrenderer 212.

Rendering in Parallel Utilizing Multiple Renderers on the Network

Alternatively, if the controller determines that the DMD signal is to beprocessed in parallel utilizing the first renderer 202 and one or moreexternal renderers, the first STB 102 receives the input video signal146 from the media device 108 and processes it via the first renderer202. The first renderer 202 may first capture and convert the inputvideo signal 146 from an analog video signal to a digital video signalbased on whether the media device 108 is an analog video device. If themedia device 108 is a digital device, then the first renderer 202 doesnot have to capture and convert the input video signal 146 except forpossibly converting the input video signal 146 from the digital formatutilized by the media device 108 to another digital format more suitablefor processing by the plurality of renderers. Part of the digital videosignal may then be rendered by the first renderer 202 to produce part ofthe DMD signal which may be passed to the first STB storage 138 viasignal path 142. In this manner the first STB storage 138 may act as alocal archive for DMD that is uploaded by the user utilizing the mediadevice 108.

Another part of the digital video signal may then be rendered by thesecond renderer 210 to produce another part of DMD signal which may bepassed to the first STB storage 138 via signal paths 214, 132, 110, and142 and through the second STB 118, network 104 and first STB 102. Thissecond part of the DMD signal may be combined with the first part of theDMD signal to make the combined DMD signal 148. Moreover, another partof the digital video signal may then be rendered by the third renderer218 to produce yet another part of DMD signal which may be passed to thefirst STB storage 138 via signal paths 222, 134, 110, and 142 andthrough the third STB 120, network 104 and first STB 102. This thirdpart of the DMD signal may also be combined with the first and secondparts of the DMD signal to make the combined DMD signal 148.

Additionally, another part of the digital video signal may then berendered by the server renderer 206 to produce yet another part of DMDsignal which may be passed to the first STB storage 138 via signal paths208, 130, 110, and 142 and through the server 116, network 104 and firstSTB 102. This fourth part of the DMD signal may also be combined withthe first, second and thirds parts of the DMD signal to make thecombined DMD signal 148. Further still, another part of the digitalvideo signal may then be rendered by a plurality of renderers atdifferent corresponding STBs to produce more parts of DMD signal whichmay be passed to the first STB storage 138. These plurality of parts ofthe DMD signal may also be combined with the first and second parts ofthe DMD signal to make the combined DMD signal 148.

It is appreciated by those skilled in the art that number of externalrenderers utilized is based on the system resources of the DMSS 100 andavailable bandwidth of these renderers. It is also appreciated thatwhile the server renderer 206 is potentially the most powerful renderer(or renderers based on the number of servers on the network), it maystill be beneficial to utilize the renderers in a plurality of STBs inorder to speed up any rendering tasks using known parallelizationtechniques.

FIG. 3 shows a flow chart 300 illustrating the example process performedby the DMSS described above in accordance with the disclosure. Ingeneral, the process starts, in step 302, by receiving an input videosignal from a media device at the first STB of the plurality of STBs.The first STB then determines, in step 304, if the input video signal isin a digital format capable of being processed directly by the first STBor whether it needs to be captured with video capture so a to produce adigital input video signal capable of being processed directly by thefirst STB, server, or other STBs on the network. The input video signalmay need to be captured if it is an analog video signal or is a digitalvideo signal in a format that needs to be converted so as to becompatible with the first STB, server, or other STBs on the network. Ifthe input video signal needs to be captured, the input video signal iscapture to produce the digital input signal, in step 306. The processthen determines, in step 308, whether to use the first renderer, anexternal renderer, or a combination of the first renderer and externalrenderers.

If the input video signal does not need to be captured, the input videosignal is the digital input signal and the process continued todetermination step 308. As stated earlier, the process then determines,in step 308, whether to use the first renderer, an external renderer, ora combination of the first renderer and external renderers.

If no external renderers are to be utilized the process continues tostep 310. The first STB render then renders the digital input signal toproduce the DMD signal. The process then continues to determination step312, where the first STB determines whether the DMD signal is to bestored on the first STB storage or external storage. If it is determinedthat the DMD signal is to be stored on the first STB storage, theprocess continues to step 314, where the DMD signal is stored on thefirst STB storage, which may be either internal or external (such as,for example, connected via USB, HDMI, Firewire®, eSATA, IEEE 802.11,Bluetooth®, Ethernet, LAN, white space device, or other type of wired orwireless connection) to the first STB. The process then ends.

Alternatively, if it is determined that the DMD signal is not to bestored on the first STB storage, the process continues to determinationstep 316. In determination step 316, if the DMD signal is to be storedon another STB storage (such as, for example, the STB storage of anotheruser that the first user desires to send the video to), the processcontinues to step 318, where the DMD signal is stored on the other STBstorage. If, instead, it is determined that DMD signal is to be storedon the server storage, the process continues to step 320, where the DMDsignal is stored on the server storage. The process then ends.

Returning to determination step 308, if external renderers are to beutilized the process continues to determination step 322. Indetermination step 322, if no other STB renderers are to be utilized,the process continues to step 324, where the input digital signal isrendered with the server renderer to produce the DMD signal. The processthen continues to determination step 312, where the first STB determineswhether the DMD signal is to be stored on the first STB storage orexternal storage. If it is determined that the DMD signal is to bestored on the first STB storage, the process continues to step 314,where the DMD signal is stored on the first STB storage, which may beeither internal or external to the first STB. The process then ends.

Alternatively, if it is determined that the DMD signal is not to bestored on the first STB storage, the process continues to determinationstep 316. In determination step 316, if the DMD signal is to be storedon another STB storage (such as, for example, the STB storage of anotheruser that the first user desires to send the video to), the processcontinues to step 318, where the DMD signal is stored on the other STBstorage. If, instead, it is determined that DMD signal is to be storedon the server storage, the process continues to step 320, where the DMDsignal is stored on the server storage. The process then ends.

Returning to determination step 322, if another STB renderer is to beutilized, the process continues to step 326. In step 326, the number ofother STB renderers are determined and their identification andlocations on the network are determined. In step 328, the input digitalsignal is send to the other STB renders. The input digital signal isthen rendered utilizing the one of more of the other STB renders toproduce the DMD signal. The process then continues to determination step312, where the first STB determines whether the DMD signal is to bestored on the first STB storage or external storage. If it is determinedthat the DMD signal is to be stored on the first STB storage, theprocess continues to step 314, where the DMD signal is stored on thefirst STB storage, which may be either internal or external to the firstSTB. The process then ends.

Alternatively, if it is determined that the DMD signal is not to bestored on the first STB storage, the process continues to determinationstep 316. In determination step 316, if the DMD signal is to be storedon another STB storage (such as, for example, the STB storage of anotheruser that the first user desires to send the video to), the processcontinues to step 318, where the DMD signal is stored on the other STBstorage. If, instead, it is determined that DMD signal is to be storedon the server storage, the process continues to step 320, where the DMDsignal is stored on the server storage. The process then ends.

Sharing Digital Media Data

Turning back to FIG. 2, the DMSS 200 allows sharing of DMD betweendifferent users (each having a corresponding STB) in the network 104.The users and their corresponding STBs may act as peers in apeer-to-peer network. FIG. 4 shows a block diagram of an example of animplementation of DMSS 400 to share DMD between STBs, mobile devices,and archives in accordance with the disclosure. In this example, theDMSS 400 includes a first STB 402, second STB 404, server 406, and firstnetwork 408. The first STB 402, second STB 404, and server 406 may be insignal communication with the first network 408 via signal paths 410,412, and 414, respectively. The first STB 402 may be in signalcommunication with a media device 416 (such as, for example, a videocamera, mobile device with a built-in video camera, or other type ofdevice) and may include a first renderer 418 and first storage device420. Similarly, the second STB 404 may be in signal communication with adisplay device 422 (such as, for example, a television, video monitor,computer monitor, or other type of video device) and may include asecond renderer 424 and second storage device 426. The server 406 mayinclude a server renderer 428 and a server storage device 430. It isappreciated that while on a first STB 402 and second STB 404 are shownfor illustration purposes, the first network 408 may have any pluralityof STBs (not shown) in signal communication with the first network 408.

Sharing Digital Media Data within the Network

Within the first network 408, the STBs may share DMD. Specifically, afirst user at the first STB 402 may share DMD on the first STB 402 witha second user at the second STB 404. As described above, the first usermay capture video from the media device 416 at the first STB 402, whichis processed to generate the DMD. Again as described above, theprocessing of the DMD may be accomplished by optionally utilizing thefirst renderer 418, the second renderer 424, the server renderer 428,other renderers (not shown) in other STBs (not shown) in signalcommunication with the first network 408, or any combination of these inparallel. Additionally, the DMD may be stored at the first storagedevice 420 and/or the server storage device 430.

The first user may allow the second user through the second STB 404 tohave access to the DMD stored on the first storage device 420 and/orserver storage device 430, which may then be displayed on the displaydevice 422. The first user may also allow other STBs (not shown) on thefirst network 408 to also access the same DMD or other DMD, i.e., if theDMD includes multiple video clips, the first user may establish rulesthat allow the second STB 404 to access certain video clips, whileestablishing different rules for other STBs to access other video clips.These rules can establish “buddy lists” that allow certain “buddies”(i.e., certain STBs) to access certain DMD while other buddies accessdifferent DMD.

Sharing Digital Media Data Outside the Network

The STBs may also share DMD outside the first network 408. Specifically,the STBs may also share DMD to mobile devices external to the firstnetwork 408 and/or to STBs on other networks. As an example, the firstnetwork 408 may be in signal communication with the Internet 432 and asecond network 434 through the Internet 432 and signal paths 436 and438, respectively.

As an example, a first user at the first STB 402 may share DMD on thefirst STB 402 with a third user at a third STB 440. The third STB 440may be in signal communication with the second network 434 via signalpath 442 and may include a third renderer 444 and third storage device446. The third STB 440 may also be in signal communication with adisplay device 448 to view the DMD. The second network 434 may be, forexample, a second cable provider network. As an example, the firstnetwork 408 may be a Comcast cable network and the second network may bea Time Warner cable network.

As described above, the first user may capture video from the mediadevice 416 at the first STB 402, which is processed to generate the DMD.Again as described above, the processing of the DMD may be accomplishedby optionally utilizing the first renderer 418, the second renderer 424,the server renderer 428, other renderers (not shown) in other STBs (notshown) in signal communication with the first network 408, or anycombination of these in parallel. Additionally, the DMD may be stored atthe first storage device 420 and/or the server storage device 430.

The first user may allow the third user, through the third STB 440, tohave access to the DMD stored on the first storage device 420 and/orserver storage device 430, which may then be displayed on the displaydevice 448. The first user may also allow other STBs (not shown) on thesecond network 434 to also access the same DMD or other DMD using buddylists.

As another example, the first user at the first STB 402 may share DMD onthe first STB 402 with a fourth user at a mobile device 450. The mobiledevice 450 may be in signal communication with the Internet 432 viasignal path 452. The mobile device 450 may be a Internet 432communication device having either wired or wireless connections to theInternet 432. The mobile device 450 may be, for example, an 802.11enabled Apple Ipod® device or other similar type of video device.Additionally, the mobile device 450 may be cellular mobile device suchas a cellular telephone with video capability. If the mobile device 450is a cellular mobile device, the signal path 452 may include a cellularnetwork (not shown) that communicates between the mobile device 450 andthe Internet 432.

Again, as described above, the first user may capture video from themedia device 416 at the first STB 402, which is processed to generatethe DMD. The processing of the DMD may be accomplished by optionallyutilizing the first renderer 418, the second renderer 424, the serverrenderer 428, other renderers (not shown) in other STBs (not shown) insignal communication with the first network 408, or any combination ofthese in parallel. Additionally, the DMD may be stored at the firststorage device 420 and/or the server storage device 430.

The first user may allow the fourth user, through the mobile device 450,to have access to the DMD stored on the first storage device 420 and/orserver storage device 430, which may then be displayed on the mobiledevice 450. The first user may also allow other mobile devices (notshown) to also access the same DMD or other DMD using buddy lists.

Peer-to-Peer Buddy Lists

In general, a cable provider of the first network 408 maintains a domainname server on the first network 408, which may be the server 406 oranother server (not shown). All the STBs on the first network 408 havemachine access control (“MAC”) addresses, where each MAC address is aunique identifier assigned a specific STB that is used in the mediaaccess control protocol sub-layer. A new pathway to provide a moresecure peer-to-peer transfer of shared DMD is a MACNS which links a MACaddress to the domain name server (“MACNS”) this is a form of identityinformation. Generally, a domain name server is not truly secure anduses layer of software (variable) and identifiers such as the user nameand/or password to authenticate. A MACNS uses multiple layers to securethat “sharee” STB and “sharer” STB (i.e., the peer 1 and peer 2) are infact the parties whom believe each other are communicating with.

A third level of ID number or password may be layered over the MACNS asan option and this can be another form of identity information. Becausecable providers may also maintain a Peer subscriber's current Internetprotocol (“IP”) address (which can be dynamic), the MACNS may requirefiltering through the cable provider servers to update any IP addresschange.

Registering STB to Global Buddy List

A Peer signs on to register themselves to a Buddy list. Part ofregistration includes the inclusion of the peer's STB MAC address in adatabase managed by a third party such as a cable provider, a gamingsystem manufacture, a service provider such as Facebook®, Google®,Apple® Myspace®, Netflix®, or AOL®. The database manager has a record ofits subscribers MAC addresses and knows the DNS/IP address therebyforming the MACNS for Peer 1. The peer registration may include at leastone of a “Handle” (aka a nickname), peer's actual name, billingtelephone number and zip code for their STB service or system, providername, receiver ID, cablecard id, access ID, STB serial number, etc.

Peer 1 may create a Buddy list (that includes other peers) that Peer 1is authorizing for sharing and there may be degrees of authorizationlinked to different Buddies on the list (i.e. size of shared files,frequency, whether the file is automatically archived). Once a peeraccount is created, a peer-name and/or password may be provided and/orcreated to give Peer 1 remote access to the buddy lists.

Finding a Buddy

In some exemplary implementation wherein the service provider is a cableprovider (as opposed to Myspace®, Netflix®, or AOL®, Facebook®, Google®,Apple® or the like). Peer 1 (the sharer) wants to share with a specificBuddy (Peer 2) but Buddy is not already one of Peer 1's Buddies. Peer 1is prompted by an STB menu to enter certain data criteria to identifyBuddy (Peer 2). This may include any account registration informationsuch as that type Peer 1 provided a CTP to create a peer's account.

The cable provider then takes the data provided by Peer 1 and conveysthe data about Buddy (Peer 2) to Buddy's STB. Buddy's STB determines ifPeer 1 has share rights to Buddy (Peer 2). If not the STB for Buddynotifies Buddy and requests authorization for Peer 1. If the STB forBuddy cannot authorize Peer 1 then no share. Otherwise sharing issupported. If Peer 1 is approved then STB for Buddy provides STB forPeer 1 Buddy's complete MACNS plus Buddy's active IP address.

Once Buddy is found, all relevant data is stored locally, includingBuddy name, MACNS address for future authentication and current IPaddress (queried later to ensure validity, as IP addresses tend to bestart by nature) when wanting to receive/transmit digital media. Once aBuddy is approved, Buddy's STB is authenticated and direct sharing fromPeer 1 to Peer 2 at whatever approved level can commence.

Managing Buddies and Lists

Buddy lists are listed by Peer 1, Peer 1 may add a preferred identifier.The following example is a non-exclusive list of some examples of suchidentifiers: age, location, attribute (female, male grandparent,siblings) image, group affiliation, nickname or full user name. Buddylists can also be configured into groups or types of Buddies, dependingon relationships.

Optionally, Peer 1 is able to set preferences to each Buddy individuallyvs. global settings. These specific preferences include, but not limitedto:

-   -   File size—limit the amount of file size a Buddy can send per        file. If file size is too large due to preferences, or exceeds        available space the option to send a re-sized copy is optional.    -   File type—limit the typed of video codes acceptable (WM, MOV,        H.264, Xvid, mpeg1, mpeg2, DV-AVI, Divx, MKV, and other known        file formats and containers, including the native DVR file        formats. Frequency how often per period a buddy can send Peer 1        DMD.

Content, files may be prescreened by Peer 1's STB (which may be at leastone of cablebox, gaming system, gaming unit, PlayStation®, Nintendo®,Wii®, Xbox®, Apple® tv, DVR, and the like) and files with questionablecontent (beyond a rating level i.e. family, teen, adult) may be refusedor quarantined. Buddy if so chosen via preferences can be given direct,point to point access to both local STB content and/or to remote storageto view available content. Including publically available video orprivate content—determined by preferences relevant to the Buddy.

Shown in FIGS. 5 through 16 are example screen shots of a graphical userinterface (GUI) to some aspects of the disclosure. All callouts in thesefigures are hereby incorporated as if fully set forth herein.

Shown in FIGS. 17-19 are exemplary implementations of identifying theends of a DMD file (500) which has ends forming a start boundary (502)and a stop boundary (504). On aspect of this disclosure is the use of ashared DMD file to act as a vehicle, Trojan horse, canvas or piggy backfor one of a brand, message and advertisement file which may be referredto as Message Media or “MM”. Examples of MM that may be connected orembedded to a DMD file include but are not limited to sound, video,still image, video game, service, product, TV or movie trailer. FIG. 18illustrates one or more MM files (600, 650) each with a start (602,652)and a stop (604, 654) connected a DMD file (500). MM files may be one ormore and they may be contiguous, or separate. MM files may attach ateither end of the DMD file. Those of ordinary skill in the art will alsounderstand that an MM file may also be inserted in the midst of the toshare DMD and such is within the scope of this disclosure. When a DMDfile is targeted to be a carrier of a MM file it may also be identifiedas a Target DMD file or TDMD as it is targeted by the advertiser orother seeking to piggy back or add content to the share DMD.

The insertion of MM to a share DMD may be automatic, via proxy or on acase by case basis. The insertion may be surrounded by promptscommunicated to the sharer and may also ask for or require sharer'sacceptance of adding a MM file. Alternatively as a promotion method asponsor who may also defray costs of digital sharing of personal mediacould exchange agreement to have or to accept MM inserted in a share DMDin exchange for reduced costs, or accumulation of benefits when usingthe DMD sharing system. A revenue model associated with MM add-onsincludes charging a fee to advertisers for the addition of the MM to theshare file.

Said MM content may come from a plethora of sources. It may be reside atthe server side or the local side. The MM may be uploaded to the localSTB (which may be at least one of cablebox, gaming system, gaming unit,PlayStation®, Nintendo®, Wii®, Xbox®, Apple® tv, DVR, and the like) ateither the sharee or sharer side and may be added to a DMD file before ashare, during preparation for a share (thereby excluding an archive),prior to archive, on the receipt side of the sharee or during theplayback preparation. Such content may be general for example a versionof a product advertisement for television/broadcast. Such content may benarrowly item specific including but not limited to new movies, sportingevents, sales, other events. Such content may be geographic specificbased on the location of the likely viewer (buddy). Such content may bedate or time specific. Note, a user or buddy may optionally have thechoice via the interface to archive or to not archive the MM associatedwith the share DMD.

In FIG. 19 rather than physically adding the MM at the to share DMDfile, a time gap (700) or allocation is identified with specified start(702) and stop (704) codes. Said gap is of a defined period i.e. 10seconds, 20 seconds, 35 seconds . . . n seconds. The gap identifies anopportunity to insert MM. Utilizing said gap as opposed to locking downa particular content for the MM provides a platform that can draw fromthe user or buddy side and or local host. The gap offers the opportunityto insert very current, very local or very targeted MM content which mayhave a higher probability to being the type of content the recipientwould resonate with. Said MM content filling the time gap would resideat the server side or on the local side of the sharee.

FIGS. 20-22 illustrate some aspects of one exemplary implementation tooverlay a MM onto at least a portion of the DMD file (500). In additionto regular MM, said overlay MM (800) may include logos or what is knownby the those in the art as “bugs” which may be added over the DMD filesolid or partially transparent.

FIGS. 21 and 22 are illustrative of a portion of a frame by frameoverlay of MM. Frame 1 (510) is a platform for a first overlay (902).The second frame (520) is a platform for a second overlay (904). Thethird frame (530) is a platform for a third overlay (906). The fourthframe (540) is a platform for a fourth overlay (908). The fifth frame(550) is without overlay. The sixth frame (560) is a platform for afifth overlay (910).

All callouts in all figures are incorporated by this reference as iffully set forth herein.

While the method and agent have been described in terms of what arepresently considered to be the most practical implementations andaspects thereof, it is to be understood that the disclosure need not belimited to the disclosed implementations, aspects or order and/orsequence of combination of aspects. It is intended to cover variousmodifications and similar arrangements included within the spirit andscope of the claims, the scope of which should be accorded the broadestinterpretation so as to encompass all such modifications and similarstructures. The present disclosure includes any and all implementationsof the following claims.

It should also be understood that a variety of changes may be madewithout departing from the essence of the disclosure. Such changes arealso implicitly included in the description. They still fall within thescope of this disclosure. It should be understood that this disclosureis intended to yield a patent covering numerous aspects bothindependently and as an overall system and in both method and apparatusmodes.

Further, each of the various elements of the disclosure and claims mayalso be achieved in a variety of manners. This disclosure should beunderstood to encompass each such variation, be it a variation of animplementation of any apparatus implementation, a method or processimplementation, or even merely a variation of any element of these.

Particularly, it should be understood that as the disclosure relates toelements of the implementation, the words for each element may beexpressed by equivalent apparatus terms or method terms—even if only thefunction or result is the same.

Such equivalent, broader, or even more generic terms should beconsidered to be encompassed in the description of each element oraction. Such terms can be substituted where desired to make explicit theimplicitly broad coverage to which this disclosure is entitled.

It should be understood that all actions may be expressed as a means fortaking that action or as an element which causes that action.

Similarly, each physical element disclosed should be understood toencompass a disclosure of the action which that physical elementfacilitates.

Any patents, publications, or other references mentioned in thisapplication for patent are hereby incorporated by reference. Inaddition, as to each term used it should be understood that unless itsutilization in this application is inconsistent with suchinterpretation, common dictionary definitions should be understood asincorporated for each term and all definitions, alternative terms, andsynonyms such as contained in at least one of a standard technicaldictionary recognized by artisans and the Random House Webster'sUnabridged Dictionary, latest edition are hereby incorporated byreference.

Finally, all referenced listed in the Information Disclosure Statementor other information statement filed with the application are herebyappended and hereby incorporated by reference; however, as to each ofthe above, to the extent that such information or statementsincorporated by reference might be considered inconsistent with thepatenting, such statements are expressly not to be considered as made bythe applicant(s).

In this regard it should be understood that for practical reasons and soas to avoid adding potentially hundreds of claims, the applicant haspresented claims with initial dependencies only.

Support should be understood to exist to the degree required under newmatter laws—including but not limited to United States Patent Law 35 USC132 or other such laws—to permit the addition of any of the variousdependencies or other elements presented under one independent claim orconcept as dependencies or elements under any other independent claim orconcept.

To the extent that insubstantial substitutes are made, to the extentthat the applicant did not in fact draft any claim so as to literallyencompass any particular embodiment, and to the extent otherwiseapplicable, the applicant should not be understood to have in any wayintended to or actually relinquished such coverage as the applicantsimply may not have been able to anticipate all eventualities; oneskilled in the art, should not be reasonably expected to have drafted aclaim that would have literally encompassed such alternatives.

Further, the use of the transitional phrase “comprising” is used tomaintain the “open-end” claims herein, according to traditional claiminterpretation. Thus, unless the context requires otherwise, it shouldbe understood that the term “compromise” or variations such as“comprises” or “comprising”, are intended to imply the inclusion of astated element or step or group of elements or steps but not theexclusion of any other element or step or group of elements or steps.Such terms should be interpreted in their most expansive forms so as toafford the applicant the broadest coverage legally permissible. Allcallouts associated with figures are hereby incorporated by thisreference.

Since certain changes may be made in the above system, method, processand or apparatus without departing from the scope of the disclosureherein involved, it is intended that all matter contained in the abovedescription, as shown in the accompanying drawing, shall be interpretedin an illustrative, and not a limiting sense.

While various embodiments of the disclosure have been described, it willbe apparent to those of ordinary skill in the art that many moreembodiments and implementations are possible within the scope of thisdisclosure. Moreover, it will be understood that the foregoingdescription of numerous implementations has been presented for purposesof illustration and description. It is not exhaustive and does not limitthe claimed disclosures to the precise forms disclosed. Modificationsand variations are possible in light of the above description or may beacquired from practicing the disclosure. The claims and theirequivalents define the scope of the disclosure. Accordingly, thedisclosure is not to be restricted except in light of the attachedclaims and their equivalents.

1. Digital content deliver comprising: a target digital media data file;a message media data file; uploading of said digital media data file toa local STB; before, during or after said upload connect said messagemedia data file to said target digital media file; and, transmit saiddigital media data file connected with said message media data to asharee.
 2. The target digital content delivery of claim 1 wherein saidmessage media is connected to the said digital media file before thestart boundary.
 3. The target digital content delivery of claim 1wherein said message media is connected to the said digital media fileafter the stop boundary.
 4. The target digital content delivery of claim1 wherein said message media is connected to the said digital mediabetween the start and stop boundaries.
 5. The target digital contentdelivery of claim 1 wherein prior to connecting said message media filewith said digital media file, said message media file resides at saidSTB.
 6. The target digital content delivery of claim 1 wherein prior toconnecting said message media file with said digital media file, saidmessage media file resides on a server remote from said STB.
 7. Thetarget digital content delivery of claim 1 wherein prior to connectingsaid message media file with said digital media file, said message mediafile resides on the sharee's STB.
 8. The target digital content deliveryof claim 1 wherein prior to connecting said message media file with saiddigital media file one of a prompt and acceptance is displayed to thesharer.
 9. The target digital content delivery of claim 1 wherein saidconnected target digital content and said message media are delivered toa share.
 10. The target digital content delivery of claim 1 whereinprior to connecting said message media file with said digital media fileone of a prompt and acceptance is displayed to the sharee.
 10. Thetarget digital content delivery of claim 1 wherein said STB is one of acablebox, gaming system, gaining unit, PlayStation®, Nintendo®, Wii®,Xbox®, Apple® tv, and DVR.
 11. Digital media messaging comprising: atarget digital media data file; a message media data file; uploading ofsaid digital media data file to a STB comprising a local gaming system;selecting a buddy to share with from a buddy list; before sharingconnect said message media data file to said target digital media; and,transmit said digital media data file connected with said message mediadata to said buddy's STB.
 12. The digital media messaging of claim 11wherein said message media is connected to the said digital media fileat least one of before the start boundary and after the stop boundary.13. The digital media messaging of claim 11 wherein said message mediais connected to the said digital media file between the start and thestop boundaries.
 14. The digital media messaging of claim 11 whereinprior to connecting said message media resides on a sever.
 15. Digitalmedia messaging comprising: a target digital media data file; a messagemedia data file; uploading of said digital media data file to a STBcomprising a gaming system; selecting a buddy to share with from a buddylist; transmit said digital media data file connected with said messagemedia data to said buddy's STB; and, connect said message media datafile to said target digital media when delivering said target digitalmedia to said buddy.
 16. The digital media messaging of claim 15 whereinsaid message media is connected to the said digital media file at leastone of before the start boundary and after the stop boundary.
 17. Thedigital media messaging of claim 15 wherein said message media isconnected to the said digital media file between the start and the stopboundaries.
 18. The digital media messaging of claim 15 wherein prior toconnecting said message media resides on said buddy's STB.